Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Aug 9, 2024

This PR contains the following updates:

Package Change Age Confidence
graphql-request (source) 6.1.0 -> 7.3.5 age confidence

Release Notes

graffle-js/graffle (graphql-request)

v7.3.5

Compare Source

What's Changed

Full Changelog: graffle-js/graffle@v7.3.0...v7.3.5

v7.3.4

Compare Source

Bug Fixes
  • Fixed #​1281: GraphQL errors and data are now accessible from 4xx/5xx HTTP responses
  • Fixed #​1461: ClientError is properly returned for non-2xx responses with malformed bodies
  • Fixed #​1462: ClientError is properly returned for non-2xx responses with unsupported content types
Changes
  • Non-2xx HTTP responses now parse the response body first to extract GraphQL errors/data when available
  • Non-2xx responses with valid GraphQL bodies return ClientError with errors and data accessible
  • Non-2xx responses with invalid bodies still return ClientError (not generic Error) for backwards compatibility
  • This release reverts PRs #​1457 and #​1459 which introduced regressions, then reapplies a minimal fix for #​1281
Breaking Changes

None - this release maintains backwards compatibility while adding support for accessing GraphQL errors from 4xx/5xx responses.

v7.3.3

Compare Source

Bug Fixes
  • Non-JSON Error Response Handling: Fixed regression in 7.3.2 where servers returning HTTP 4xx/5xx status codes with non-JSON response bodies (HTML, plain text) would throw an unhelpful error: "Invalid execution result: result is not object or array" (#​1459, closes #​1458)
    • Added safe JSON parsing fallback for responses without proper Content-Type headers
    • Returns descriptive error messages with response body preview for non-JSON responses
    • Handles common production scenarios: load balancer errors (502/503 HTML pages), CDN errors, WAF/firewall responses, misconfigured servers
    • Maintains backward compatibility for servers that omit Content-Type but return valid JSON
    • Added comprehensive test coverage for HTML, plain text, and missing Content-Type scenarios
What Changed

Version 7.3.2 introduced a bug where the ELSE branch in parseResultFromResponse would pass raw strings (HTML, plain text) to a parser expecting objects/arrays. This only surfaced when:

  1. Server returns 4xx/5xx status code
  2. Content-Type header is missing or non-JSON (e.g., text/html, text/plain)
  3. Response body is not valid JSON

This is now fixed with graceful error handling and clear error messages.

v7.3.2

Compare Source

Bug Fixes
  • HTTP Error Handling: Fixed regression from v6 to v7 where HTTP 4xx/5xx responses would not include GraphQL errors from response body in ClientError (#​1457, closes #​1281)

    • Response body is now parsed before checking HTTP status
    • Users can access GraphQL errors via error.response.errors even with non-2xx status codes
    • Common use case: authentication errors (422), server errors (500)
  • graphql-codegen Compatibility: Added support for TypedDocumentString from @graphql-codegen when using documentMode: 'string' (#​1456, closes #​1453)

    • Handles boxed String objects created by TypedDocumentString class
    • Normalizes document input to prevent crashes when passing to GraphQL operations

v7.3.1

Compare Source

Bug Fixes

  • Fixed broken example links on npmjs.com (#​1332)
    • Updated package.json repository metadata to point to correct location: graffle-js/graffle
    • Updated homepage URL to include /tree/graphql-request path
    • Updated bugs URL to point to correct issues page
    • All example links on npm now correctly resolve to files in the graphql-request branch

Links

v7.3.0: graphql-request v7.3.0

Compare Source

What's Changed

Features
  • CommonJS Support: Added CommonJS module format () alongside ESM for better compatibility with Jest and other testing environments that aren't fully ESM-ready
  • Improved Type Defaults: Default type parameters to any for easier migration and reduced type friction
Pull Requests
  • feat(graphql-request): default types any and support common js #​1396

Contributors

Thanks to @​Moumouls (Antoine Cormouls) for the contribution! 🚀


Installation:

npm install [email protected]

Package: https://www.npmjs.com/package/graphql-request/v/7.3.0

v7.2.0: [email protected]

Compare Source

Features:

v7.1.2: [email protected]

Compare Source

Fixes:

  • b732f45 Remove reference to type-fest which is not a dependency.

v7.1.1: [email protected]

Compare Source

Fixes
  • 37445c8 Support CJS and remove Graffle code. To use Graffle by now, you should be using pnpm add graffle@next.

v7.1.0

Compare Source

Fixes
Improvements
  • 30b39bf improve: update all deps to latest (#​936)
  • 92ea1b2 docs: mention additional requirement for TS
  • 39dfb37 refactor: no mock server
  • db4db92 docs: TS moduleResolution requirements
Graffle
Features
Chores

v7.0.1

Compare Source

Fixes
  • dc299d9 no node fs module in runtime
Improvements
  • 11805c8 improve: remove needless deep imports into graphql
Chores

v7.0.0

Compare Source

BREAKING CHANGES
  • 2a121c6 remove inlined graphql websocket code
  • 99a192e add spec compliant default Accept header (#​618)
  • 0e53aed replace GraphQLClientRequestHeaders with built-in HeadersInit type (#​616)
  • c3a309f remove support for CommonJS (#​607)
  • 6efcc0d remove cross-fetch polyfill
  • Valid URL must be passed (no more path-only strings like /foo) (#​745)
Features
Fixes
Improvements

Graffle (alpha)

Features

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday" in timezone Europe/London, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@cypress
Copy link

cypress bot commented Aug 9, 2024

BanManager-WebUI    Run #9058

Run Properties:  status check failed Failed #9058  •  git commit c93e46ada8 ℹ️: Merge eec3d512a227e9bce8d129f94a2c65532aa3b9dd into bd7f7548bcfbf8c7388816e2f7e1...
Project BanManager-WebUI
Branch Review refs/pull/1519/merge
Run status status check failed Failed #9058
Run duration 01m 07s
Commit git commit c93e46ada8 ℹ️: Merge eec3d512a227e9bce8d129f94a2c65532aa3b9dd into bd7f7548bcfbf8c7388816e2f7e1...
Committer renovate[bot]
View all properties for this run ↗︎

Test results
Tests that failed  Failures 6
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 0
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 9
View all changes introduced in this branch ↗︎

Tests for review

Failed  email.spec.js • 3 failed tests

View Output Video

Test Artifacts
Account/Email > errors if incorrect current password Screenshots Video
Account/Email > errors email used Screenshots Video
Account/Email > successfully changes email Screenshots Video
Failed  password.spec.js • 3 failed tests

View Output Video

Test Artifacts
Account/Password > errors if incorrect current password Screenshots Video
Account/Password > errors if new password weak Screenshots Video
Account/Password > successfully changes password Screenshots Video

@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch 6 times, most recently from 0102f19 to 6e41f44 Compare August 16, 2024 06:34
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch from 6e41f44 to f5f856f Compare August 18, 2024 03:10
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch 9 times, most recently from ab351e6 to b10d007 Compare September 24, 2024 06:20
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch 8 times, most recently from 5a18500 to ae270a5 Compare September 30, 2024 07:41
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch 5 times, most recently from 4e021d7 to d30ee4a Compare October 4, 2024 04:19
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch 7 times, most recently from 39641ff to 6225c59 Compare March 22, 2025 05:32
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch 5 times, most recently from 82b772c to 98de969 Compare March 27, 2025 10:37
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch 3 times, most recently from 854fac0 to 7882cb6 Compare April 1, 2025 13:03
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch from 7882cb6 to 151dd45 Compare April 11, 2025 03:09
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch from 151dd45 to 6c3d6b9 Compare May 26, 2025 03:51
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch from 6c3d6b9 to 3a9646f Compare June 16, 2025 19:14
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch from 3a9646f to 8abea15 Compare September 8, 2025 02:31
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch 2 times, most recently from 09028cb to 72b9feb Compare October 18, 2025 20:53
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch from 72b9feb to 2e7933d Compare October 29, 2025 01:44
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch 3 times, most recently from 697c8e4 to 1acca12 Compare November 16, 2025 05:11
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch from 1acca12 to b8e6ea9 Compare November 18, 2025 02:28
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch from b8e6ea9 to ca21c5c Compare November 25, 2025 18:26
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch from ca21c5c to 925bed4 Compare December 4, 2025 10:46
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch from 925bed4 to eec3d51 Compare December 4, 2025 12:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant